AI Automated Review

Full PR review.

Analysis engine: MiniMax-M2.7@https://litellm.jory.dev/v1 (anthropic) — routed smart (risk match: public_route_changes)

Review Summary

Recommendation: Approve — The PR implements linked PR follow-up as a first-class task type in the /api/agents/[agentName]/next-task endpoint. Changes are minimal, well-tested, and align with issue PR 397 acceptance criteria.

Change-by-Change Analysis

src/app/api/agents/[agentName]/next-task/route.ts (28 additions)

The route handler gains a scan for linked PR follow-up before returning the standard implement task. The logic:

1. Queries the agent queue (already filtered by lane, claimed status, etc.)
2. New: Uses queue.find() to locate the first issue where linkedPrHealth.needsFollowup is true with a PR number
3. Returns a followup-pr task with full issue and PR context
4. Falls back to existing implement task behavior if no follow-up needed

This maintains the documented priority order: PR-fix queue items → linked PR follow-up → normal implementation → idle.

Required Checks:

• ✅ Route access controls in place: Per AGENTS.md and README.md, agent API routes use DISPATCH_AGENT_TOKEN bearer auth via a shared authorizeRequest() helper in src/lib/auth.ts. The GET endpoint is read-only (returns task metadata), and agents authenticate via bearer token.
• ✅ No unintended public endpoints: No new routes added; only an existing endpoint's behavior is modified. No auth mode changes or route exposure.

src/app/api/agents/[agentName]/next-task/route.test.ts (307 additions)

Nine new tests cover:

• Followup task returned when issue has linked PR needing follow-up
• Followup beats normal implement work
• PR-fix queue still takes precedence (correct priority order)
• Task includes full issue context (repo, number, title, url)
• Task includes full PR context (repo, number, url)
• Followup reasons are included when present
• Fallback reason used when reasons array is empty
• Normal implement still works when no follow-up exists
• Idle still works when queue is empty

Standards Compliance

• Label conventions: Tests use priority/p0, status/ready, currentLane: "normal" — consistent with repository patterns.
• Code standards: Input validation occurs via Prisma queries; error handling uses the existing pattern; no secrets in output.
• API design: Returns appropriate HTTP 200 with JSON; task structure follows established AgentTask contract from src/lib/agent-task.ts.

Linked Issue Fit (PR 397)

Issue PR 397 acceptance criteria:

Tool Harness Findings

• src/app/api/agents/[agentName]/next-task/route.ts was read successfully; confirms imports and existing structure.
• src/app/api/agents/[agentName]/route.ts does not exist (no parent route file needed; Next.js handles this via file-system routing).
• Auth pattern matches repository conventions: bearer token via DISPATCH_AGENT_TOKEN.

Unknowns / Needs Verification

None relevant to this PR.

• No dependency upgrades requiring compatibility matrix verification.
• No Docker image changes.
• No secrets or configuration changes.

Evidence Provider Findings

No evidence providers configured for this PR.

CI Results

• Docker Build: ✅ Success
• Validate: ✅ Success (lint, typecheck, 1246 tests)

CI confirms the implementation passes all validation gates.